Skip to content

Conversation

@jasagredo
Copy link
Contributor

No description provided.

Copy link
Member

@amesgen amesgen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving the first commit as a port from #1738

The second commit commit also makes sense in general as per #1565 (comment), but it isn't really related to the first commit, and also, we didn't yet update to resource-registry-0.2 in this branch, right? So maybe move it to #1714?

Base automatically changed from js/bangs to main October 29, 2025 19:41
@jasagredo jasagredo force-pushed the js/fix-mempool-dangling-forker-forward-port branch from 13ee157 to 83a00de Compare October 31, 2025 10:40
@jasagredo jasagredo force-pushed the js/fix-mempool-dangling-forker-forward-port branch from 83a00de to 2369c86 Compare October 31, 2025 10:40
@jasagredo jasagredo enabled auto-merge October 31, 2025 10:46
@jasagredo jasagredo added this pull request to the merge queue Oct 31, 2025
Merged via the queue into main with commit 8eefcba Oct 31, 2025
18 of 21 checks passed
@jasagredo jasagredo deleted the js/fix-mempool-dangling-forker-forward-port branch October 31, 2025 14:04
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in Consensus Team Backlog Oct 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

3 participants